home *** CD-ROM | disk | FTP | other *** search
Text File | 1991-03-06 | 1.6 KB | 47 lines | [TEXT/GEOL] |
- Item 8638815 14-Sept-89 10:03
-
- From: KNEPPER Knepper, Christopher
-
- To: CH0068 CH DEV Hamilton, Bonaduz
-
- cc: MACAPP.TECH$ MACAPP Tech
-
- Sub: Re: Scroller problem
-
- Hi Thomas,
-
- >Can anyone tell me how the fields f1-f4 ,VertConstrain and HorzConstrain
- >influence the behaviour of this scroller ?
-
- I've found that the best place to look to find out what the view's fields mean
- is in ViewTypes.r. For example, in the section which describes TScroller:
-
- case Scroller:
- key literal longint = 'scrl'; // Template signature
- pstring;// Class name, "TScroller"
- align word;
- bytenoVertScrollBar, VertScrollBar;
- bytenoHorzScrollBar, HorzScrollBar;
- longint;// Vertical maximum.
- longint;// Horizontal maximum.
- integer;// Vertical scrollunits.
- integer;// Horizontal scroll units.
- bytenoVertConstrain, VertConstrain;
- bytenoHorzConstrain, HorzConstrain;
- rect; // Scroll bar offsets
-
- You'll see that f1 = Vertical maximum, f2 = Horizontal maximum, f3 = Vertical
- scrollunits, and f4 = Horizontal scroll units.
-
- Basically, VertConstrain and HorzConstrain indicate whether the translation
- values should be constrained to even multiples of f3 or f4.
-
- When VertConstrain is enabled, then the vertical scrolling is constrained to f3
- units per click in the down or up arrow of the vertical scrollbar.
-
- When HorzConstrain is enabled, then the vertical scrolling is constrained to f4
- units per click in the down or up arrow of the horizontal scrollbar.
-
- -Chris
-
-